Method and a system for email address validation

ABSTRACT

A device identifies an email address of a recipient listed in an email. The device determines whether the email address is erroneous and based on determining that the email address is erroneous, the device displays a recommended email address to a user.

FIELD OF THE INVENTION

The present invention relates generally to email address validation, andmore particularly to validating the intended recipients' email addressesby analyzing the user's mailbox and corporate email directory.

BACKGROUND

An email address identifies specific email mailbox to which the messageis to be delivered. An email address is made up of a case insensitivelocal part, a “@” symbol, and a domain part.

An email validation and verification is generally performed by theapplication programming interface (API) for syntactical correctness anddomain name verification. However, that does not always guaranteeaccurate results. To improve the validation process, identity validationis performed by requesting a user to provide additional informationabout the recipient, such as recipient's phone number, address, or bysending a special hyperlink to a previously defined email address.

SUMMARY

Embodiments of the present invention provide a system, method, andprogram product for an email address validation. A device identifies anemail address of a recipient listed in an email. The device determineswhether the email address is erroneous and based on determining that theemail address is erroneous, the device displays a recommended emailaddress to a user.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an email validation system, in accordance with anembodiment of the invention.

FIG. 2 is a flowchart illustrating the operations of an email addressvalidation program of FIG. 1, in accordance with an embodiment of theinvention.

FIG. 3 is a block diagram depicting the hardware components of the emailaddress validation system of FIG. 1, in accordance with an embodiment ofthe invention.

DETAILED DESCRIPTION

FIG. 1 illustrates an email address validation system 100, in accordancewith an embodiment of the invention. In an example embodiment, emailaddress validation system 100 includes a user device 110 and a server140, interconnected via network 198.

In accordance with an embodiment of the invention, network 198 is theInternet, representing a worldwide collection of networks and gatewaysto support communications between devices connected to the Internet.Network 198 may include, for example, wired, wireless or fiber opticconnections. In other embodiments, network 198 may be implemented as anintranet, a local area network (LAN), or a wide area network (WAN). Ingeneral, network 198 may be any combination of connections and protocolsthat will support communications between server 140 and user device 110.

According to an example embodiment, server 140 stores and operates acorporate directory 142, which contains employees' information of anorganization. Server 140 may be a web server, file server, desktopcomputer, or any other electronic device or computing system capable ofreceiving and sending data to and from other computing devices such asuser device 110 via network 198. Although not shown, optionally, server140 may comprise a cluster of servers. In an exemplary embodiment,server 140 is a computing device that is optimized for the support ofmultiple network requests related to accessing, searching and updatingthe corporate directory information.

In the example embodiment, corporate directory 142 is maintained onserver 140, and may be stored in the format of a database that allowsaccess, search, and update by a program running on a user device 110.Corporate directory 142 includes detailed employee information that isrelevant to a particular corporation such as the name of an employee, anID number of an employee, an address of an employee, current andprevious roles of an employee in the company, an email address of anemployee, current and previous job title of an employee, phone number ofan employee, photograph of an employee and any additional informationthat the employer needs for the operation of his business.

In the example embodiment, user device 110 includes email program 112and email address validation program 114. User device 110 may be adesktop computer, a notebook, a laptop computer, a tablet computer, ahandheld device, a smart-phone, a thin client, or any other electronicdevice or computing system capable of receiving and sending emails toand from other computing devices, and receiving data related to theemail addresses, such as accessing and searching the corporate directory142 stored on the server 140 via network 198.

According to an embodiment, email program 112 is a software programcapable of receiving, sending, and displaying email information to theuser. In addition, email program 112 may access the corporate directory142 on server 140 via network 198. In another embodiment, email program112 may be located on server 140 or another server in network 198 andrender the information to the user device 110.

In the example embodiment, email address validation program 114(hereinafter “validation program”) is a software program that is capableof identifying user intended recipients' email address(es) entered bythe user, and validating them based on email content, corporatedirectory information, and content of the previous emails stored inuser's email folder. In the example embodiment, the validation programis an add-on to email program 112. In other embodiments, the validationprogram may be either an integration software or a standalone softwarelocated on either server 140 or on other servers. The validation programis in communication with user device 110 via network 198. The operationsand functions of the validation program are described in further detailsbelow with regard to FIG. 2.

FIG. 2 is a flowchart illustrating the operations of the validationprogram of FIG. 1. The flowchart in FIG. 2 outlines an exampleembodiment of email address validation program 114 in assessing theaccuracy of the user entered email address by: (i) determining whetherthe intended recipient's role or job has changed since the user lastcontacted the same recipient and recommending to change the recipient'semail address to an updated email address(es) of a person(s) that nowhave that role; (ii) checking the content of the email and identifyingpotential recipients and suggesting to add them as an additionalrecipients; (iii) checking the email address(es) for possible spellingerrors and updating the email address accordingly; and (iv) determiningwhether the email content is intended to be a secure transmission byanalyzing its content and if yes, alerting and suggesting to remove therecipient if the email address of the recipient is not found in theuser's sent folder.

According to example embodiment, validation program identifies anintended recipient email address(es) (step 205). In the exampleembodiment, validation program identifies and compares the intendedrecipient's email address(es) to the corporate directory and usermailbox in order to assess email address validity and suggestsubstitutions or corrections of the email address to the user ifnecessary. The identification of the recipient's email address may beperformed in either (i) real time (while the user is typing or enteringthe email address) or (ii) when the user intends to send the email (i.e.by pressing the send button). In embodiments which identify recipient'semail address in real time, validation program may further suggest toadd, delete, or correct the email address by, for example, opening adrop down menu with suggestions, or by auto-correcting a matchingrecipient's email address based on corresponding role or job title. Inother embodiments, validation program may process multiple email addressentries in the same way as a single email address by analyzing each oneof them and giving suggestions after analyzing all of the emailaddresses identified by the validation program. In further embodiments,for example, when validation program is not integrated to the emailprogram or service, it may identify an email address entered by the userby using a real-time analysis of the input device (such as keyboard) oran IO stream of the device (operating system). For example, emailidentification may be performed by the validation program anytime whenthe user enters a “@” symbol the validation program may extract theemail address by recovering the text directly before and after thesymbol. In further embodiments, validation program may determine therecipient's email address by using a natural language processing oroptical character recognition algorithms.

In accordance with an embodiment, validation program determines if therecipient's role or job title (hereinafter “position”) has changed(decision 210). In order to assess whether the recipient is the intendedrecipient, the validation program determines if the recipient has a newposition in order to ensure that an email which is intended for aspecific position holder, rather than a specific person, reaches theappropriate inbox. In the example embodiment, validation program checksthe recipient's records of roles and job titles in corporate directory142, located on server 140, via network 198. In other embodiments, thevalidation program may access other databases that contain at leastemail addresses, and position records including corresponding dates theindividual took or quit his position. Alternatively, validation programmay track the changes in the recipient's position from the local mailboxof the user, should the mailbox contain this information. Afteridentifying records of the intended recipient's position and dates fromthe corporate directory, validation program determines if the positionchange occurred after transmission of the most recent correspondencebetween the user and the recipient.

In another embodiment, the validation program may compare whether therecipient's position has changed within a specific duration of time thatwas either pre-defined by the validation program or prioritized by theuser. For example, if the duration was set to 30 days, the validationprogram checks whether the recipient's position has changed within thelast 30 days. For example, if the user inputs Alpha's email address asan intended recipient and the validation program determines Alpha'sposition from the corporate directory 142 as an IT specialist,validation program 114 then determines whether Alpha is still thecurrent IT specialist. If his position has changed, the validationprogram determines if his position changed before or after the usertransmitted a previously sent email to Alpha.

In example embodiment, if the validation program determines that therecipient's position has changed (decision 210, “YES” branch), thenvalidation program determines and stores recommendation to add newrecipient email address(es) of one who currently holds the position ofthe original recipient before it was changed and stores recommendationto replace recipient's email address (step 215). The determination andstorage of the replacement recipients is leveraged when making futurerecommendations, to the user, to change the intended recipient beforeemail transmittal. In other embodiments, validation program may make asuggestion right away without storing the email addresses. In accordancewith the embodiment, validation program searches corporate directory 142or other relevant email databases for the recipients who currently holdintended recipient's position before the change and stores their namesand email addresses as replacement recipients in order to recommend themto the user. For example, if the user enters Alpha's email address whowas an IT specialist when the user last contacted him by email, thevalidation program will search the corporate directory 142 and determinethat Alpha is no longer holding the IT specialist position (i.e. his jobtitle is different). Then validation program will search and determinereplacement recipients' names and email addresses of the individualsfrom the corporate directory 142, preferably from the same geographiclocation whose job title is an IT specialist. If the validation programdetermines from the corporate directory that IT specialist position wassplit between Beta and Gamma, the validation program will determine andstore both emails with the recommendation to add Beta and Gamma asreplacement recipients and remove Alpha as an intended recipient.

If validation program 114 determines that the recipient's role or jobtitle has not changed (decision 210, “NO” branch) or if validationprogram already determined and stored recommendation to add newrecipient email address(es) (step 215), validation program proceeds todetermining whether the email content includes names, roles, or jobtitles of any potential recipients that are not on the intendedrecipients list of addresses (decision 220). This determination isrequired in order to validate and suggest to the user to add or removerecipients according to the email content. In the example embodiment,validation program determines whether email content includes names orpositions by comparing the content of the email to corporate directory142 and determining potential recipient's email address. Thedetermination of names and positions of the potential recipient's emailaddress and his position may be made for example, by utilizing stringmatching, and/or natural language processing when comparing emailcontent to corporate directory 142. Continuing the example above, ifvalidation program determines John Doe name appears in the content ofthe email, validation program will check if John Doe appears in thecorporate directory and has an email in corporate directory 142, thenvalidation program continues to determining if the user sent him emailtransmissions before (decision 225).

If validation program determined that email content includes names,roles, or job titles related to potential recipients who are on thecorporate directory 142 (decision 220, “YES” branch), then validationprogram checks if the user sent any email transmissions previously tothat potential recipient, (decision 225). In addition, validationprogram determines whether potential recipient's email address appearsin the user mailbox by referencing email program 112. For example, ifthe email contained John Doe, who was not a recipient, the validationprogram will reference corporate directory and then check the mailbox todetermine that the user sent any email transmission to John Doe'sbefore.

If any email was previously sent to potential recipient with thedetermined name, role, or job title (decision 225, “YES” branch), thenvalidation program determines and stores recommendation to add newrecipient (potential recipient's) email address(es) (step 230). In theexample embodiment, determining that the recipient has received an emailfrom the user before is an indication that the email should betransmitted to potential recipient and the validation program willsuggest to add the user as the potential recipient. Continuing theprevious example, after determining that “John Doe” is present in thecontent of the email, determining that John Doe is in the corporatedirectory 142, and that the user has previously sent an email to JohnDoe, the validation program will store John Doe's email address tosuggest it to the user before the email will be transmitted. In otherembodiments, validation program may only reference the corporatedirectory and if the potential recipient is in it suggest to add him tothe user without checking the user's mailbox.

If the email content does not contain a name, role or job (decision 220“NO” branch), an email has not been previously sent to the name, role,or job (decision 225 “NO” branch), or validation program alreadydetermined and stored the potential recipient email address (step 230),then validation program determines whether intended recipient's emailaddress exists in a mailbox or corporate directory (decision 235). Ifrecipient's email address may be found in corporate directory 142 thenit is an indication that the email is being transmitted to existingrecipient or the user made an error in entering the recipient's emailaddress. In the example embodiment, this validation of recipient's emailaddress is performed by searching corporate directory 142 via network198.

If the validation program finds that the intended recipient's emailaddress does not exist in a mailbox or corporate directory (decision235, “NO” branch), the validation program checks whether the emailaddress was incorrectly spelled (decision 240). In the exampleembodiment, the validation program will check the email address forerrors by comparing it to the email addresses stored in the corporatedirectory 142 and in the mailbox of the user by running, for example, afuzzy string searching algorithms and determining by approximation thecorrect email address(es). For example, if the user entered an emailaddress of John Doe as “johndo@abcde.com” the validation program willsearch the corporate directory and utilize fuzzy string searchingalgorithms in order to determine that the closest email address with theleast addition or deletion of letters as possible.

If the validation program discovers that the intended recipient's emailaddress is spelled incorrectly (decision 240, “YES” branch), thevalidation program determines and stores recommendation to add newrecipient email address(es) (step 245). For example, if the closestemail address name to the misspelled address in the corporate directory142 will be “johndoe@abcde.com”, the validation program will store andsuggest this email to the user.

If the recipient's email address exists in the mailbox or corporatedirectory (decision 235, “YES” branch), the validation program may notdetermine that the email address was incorrectly spelled (decision 240,“NO” branch), or after determining and storing the correct email address(step 245), then validation program checks whether the email content isintended to be secure (decision 250). In accordance with an exampleembodiment, the validation program searches the content of the email forpre-defined keywords or flags that trigger the validation program totreat the current email as intended to be a secure transmission. In theexample embodiment, the pre-defined keywords may be stored on adatabase, server 140, or locally on user device 110. For example,validation program utilizes string matching techniques to compare thecontent of the email to a database containing a pre-defined set ofkeywords. If any of the content of the email matches one or morekeywords contained in the database, the email is flagged as secured. Forexample, if the content of the email contains words such as:“confidential”, “secret”, which are also contained within the databaseof pre-defined keywords, validation program identifies the email contentas intended to be a secure transmission (flagged as secured).Alternatively, if validation program determines that the secure flagassociated with the email was turned on by the user (in the emailapplication), validation program identifies the email content asintended to be a secure transmission.

According to the example embodiment, if the email content is identifiedas intended to be secure (decision 250, “YES” branch), then validationprogram checks whether the recipient's email address exists in theuser's sent mail folder (decision 255). By checking if any email waspreviously sent to the intended recipient, validation program reaffirmsthat the intended recipient is the correct recipient. If the recipient'semail address does not exist in the mailbox (decision 255, “NO” branch)the validation program proceeds to remove the recipient's email addressfrom the intended recipients (step 260).

According to the example embodiment, validation program removes therecipient's email address from the intended recipient list. In anotherembodiment, validation program may suggest to remove the recipient'semail address and remove it only after the user approves or reaffirmsthe removal. In further embodiments, if the user chooses to remove theintended recipient, validation program will update its internal databasethat the removed email is not intended for secure content, and referencethe database whenever the email content is intended to be secure.

In accordance with an embodiment, if the validation program identifiesthat the email is not intended to be secure (decision 240, “NO” branch)or the email is intended to be secure but recipient's email addressexists in a mailbox (decision 255, “YES” branch), or when proceedingafter removal of the intended recipient's email address (step 260), thevalidation program proceeds to making a final recommendations to theuser (step 265) based on previously determined and stored emailaddresses and recommendations (from steps 230, 245, 260). In the exampleembodiment, the validation program arranges the potential recipient'snames and corresponding email addresses alphabetically, removes theduplicate addresses and presents them to the user. For example, thepresentation to the user may be as a dropdown menu, a pop-up window ordirect field insertion or traverse of the email address in the case whenvalidation program suggests to remove the email address as incorrectlyspelled or not appropriate. In another embodiment, the validationprogram may include reasons for making the recommendations and allow theuser to make an informed decision based on these reasons. In furtherembodiment, the validation program may allow the user to change, corrector reject the recommendations and the validation program will storethese preferences and apply them in the future analyses.

The descriptions of the various embodiments of the present inventioni.e. whether to run the validation program in real time or after theuser intends to send the email, whether the validation program checksonly corporate directory or other accessible databases, whether thevalidation program is located on the user device 110 or on server 140have been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the disclosed embodiments. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

FIG. 3 depicts a block diagram of components of a user device 110 andserver 140, in accordance with an illustrative embodiment of the presentinvention. It should be appreciated that FIG. 3 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.

A user device 110 and a server 140 include communications fabric 902,which provides communications between computer processor(s) 904, memory906, persistent storage 908, communications unit 912, and input/output(I/O) interface(s) 914. Communications fabric 902 may be implementedwith any architecture designed for passing data and/or controlinformation between processors (such as microprocessors, communicationsand network processors, etc.), system memory, peripheral devices, andany other hardware components within a system. For example,communications fabric 902 may be implemented with one or more buses.

Memory 906 and persistent storage 908 are computer-readable storagemedia. In this embodiment, memory 906 includes random access memory(RAM) 916 and cache memory 918. In general, memory 906 may include anysuitable volatile or non-volatile computer-readable storage media.

The validation program and email program 112 in user device 110, andcorporate directory 142 in server 140 are stored in persistent storage908 for execution by one or more of the respective computer processors904 via one or more memories of memory 906. In this embodiment,persistent storage 908 includes a magnetic hard disk drive.Alternatively, or in addition to a magnetic hard disk drive, persistentstorage 908 may include a solid-state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer-readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 908 may also be removable. Forexample, a removable hard drive may be used for persistent storage 908.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer-readable storage medium that is part of persistent storage 908.

Communications unit 912, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 912 includes one or more network interface cards.Communications unit 912 may provide communications using one or both ofphysical and wireless communications links. The validation program andemail program 112 in user device 110, and corporate directory 142 inserver 140 may be downloaded to persistent storage 908 throughcommunications unit 912.

I/O interface(s) 914 allows for input and output of data with otherdevices that may be connected to user device 110 or server 140. Forexample, I/O interface 914 may provide a connection to external devices920 such as a keyboard, keypad, a touch screen, and/or some othersuitable input device. External devices 920 may also include portablecomputer-readable storage media such as, for example, thumb drives,portable optical or magnetic disks, and memory cards. Software and dataused to practice embodiments of the present invention, e.g., thevalidation program and email program 112 in user device 110, andcorporate directory 142 in server 140 may be stored on such portablecomputer-readable storage media and may be loaded onto persistentstorage 908 via I/O interface(s) 914. I/O interface(s) 914 may alsoconnect to a display 922.

Display 922 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium may be a tangible device that mayretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein may bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, may be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that may directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, may be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A computer system for an email addressvalidation, the computer system comprising: one or more processors, oneor more computer-readable memories, one or more computer-readabletangible storage medium, and program instructions stored on at least oneof the one or more tangible storage medium for execution by at least oneof the one or more processors via at least one of the one or morememories, wherein the computer system is capable of performing a methodcomprising: identifying an email address of a recipient listed in anemail; determining whether the email address is erroneous, whereindetermining whether the email address is erroneous comprises determininga position of the recipient has changed, determining an email address iserroneous, and determining a confidentiality mismatch; whereindetermining the position of the recipient has changed comprises:determining a current position of the recipient; determining a previousposition of the recipient, wherein the previous position comprises oneor more of: a position of the recipient at a date of a previous emailtransmission, and a position of the recipient at a predetermined date;determining whether the current position is the same as the previousposition; based on determining that the current position is not the sameas the previous position, determining a new email address of a newrecipient based on the previous position; determining that the emailincludes one or more predefined specific words, wherein the predefinedspecific words are associated with a new position that is not a currentposition of the recipient; determining a new email address based on thenew position; wherein determining the confidentiality mismatchcomprises: determining that the email includes one or more predefinedspecific words, wherein the predefined specific words are associatedwith confidentiality; based on determining that the email address hasnot been previously sent by a user, displaying a recommendation to auser; wherein determining the email address is erroneous comprises:determining the email address is not in a database; determining asimilar email address in the database comprising one or more of:determining the similar email address by string matching the emailaddress to the database; determining the similar email address bypattern matching the email address to the database; determining thesimilar email address by approximate string matching the email addressto the database; and based on determining that the email address iserroneous, displaying a recommended email address to a user, wherein therecommended email address is one or more of: the new email address ofthe new recipient, the similar email address, the email address of therecipien